Balmsoft Polyglot

Description

Polyglot is a tool for adding localization capabilities to your Delphi application. The Balmsoft Polyglot uses very simple way for localization and it allows even end users to translate an application. It uses INI files for storing translations but at the same time it supports any properties ( TStrings, TCollection, special symbols in labels). The process of translation is as easy as place two components and set three properties. But there is not only run-time components for translation, Balmsoft Polyglot provides very convenient IDE extensions for generation and update translation files. Translation files are text so they suits for source control well. You can track wich rows excetly were changed since last version. It is much harder to corrupt automatic build because you don't need fully replace resources you translate only properties you want to translate and even if there is not translation application will not crash.

At the same time simple translation format allows translate with any text editor, so even your end users will be able to translate application.

Key features

• Easy-to-start - just place component and provide a couple of properties;
• Wizard for generation and update translation files;
• Easy to use translation format (just plain text);
• Special symbols support;
• Collections support;
• TStrings support;
• Switching between languages in run-time;

New in version 1.3

• Delphi 4 support;
• TbsPolyglotTranslator and TbsPolyglotManager provides set of events;
• "Generate LNG File" Wizard provides additional filtering options (by property name and by property type);
• Non visual components support ( TActions, TMainMenu);
• Non API INI file ( no INI file size limitation for Windows 9x);
• Small bug-fixes and enhancements;

New in version 1.4

• Resourcestring support (with generation);

New in version 1.5

• "Exclude properties with specific names" filter in LNG file wizard;
• "Skip properties that linked to an action" filter in LNG file wizard;
• TDataModule is supported;
• MRU list in LNG generation wizard;
• Small bug-fixes and enhancements;

Compare with resource loaders

There are two main directions in multi language support. The first one is replacing compiled resources with their translated equivalent and the second one is providing additional information for changes specific for some language. Both ways have their own advantages and disadvantages. Classical example of resource loader is Borland Integrated Translation Environment (ITE). It is a great tool and allows you to localize any resource in your application, but there are some points in to use the library like Balmsoft Polyglot:

• Simple file format allows end-users modify translations and translate an application to their mother language;
• It is easier to understand and use than resource editors;
• Any changes to translations can be stored in a version tracking software (it is text file);

For now I can see only one limitation:

• The Polyglot can not translate forms that reside in other components you use;

So You can try both and choose which one you like best. And the last argument - ITE is supplied only with Delphi Enterprise but our library is free for use. You can not get sources for ITE at all, but you can license sources for Balmsoft Polyglot.